| Package | hl7.ehrs.uv.phrsfmr2 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/uv/phrsfmr2/https://build.fhir.org/ig/HL7/phrsfm-ig/Requirements-PHRSFMR2-PH.6.3.html |
| Url | http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-PH.6.3 |
| Version | 2.0.1-ballot |
| Status | active |
| Date | 2025-04-03T15:15:30+00:00 |
| Name | PH_6_3_Communications_Between_Provider_and_PHR_Account_Holder_and_or_PHR_Account_Holder_Proxy |
| Title | PH.6.3 Communications Between Provider and PHR Account Holder and/or PHR Account Holder Proxy (Function) |
| Experimental | False |
| Authority | hl7 |
| Description | The system should enable the PHR Account Holder to capture information in preparation for an encounter with a provider and to support ongoing interactions with that provider. The system should enable the PHR Account Holder to request appointments with health care providers and capture information in preparation for the encounter. |
| Purpose | The PHR Account Holder may fulfill specific requests for data or obtain requested diagnostic studies prior to the formal encounter. This may include providing PHR-S access to the new provider. The provider could also communicate with various members of the PHR Account Holder's care team. Example(s): The PHR Account Holder MAY fill out a current Review Of Systems (ROS) template questionnaire and specific chief complaint related questions as part of the History of Present Illness (HPI) prior to the encounter. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
The system should enable the PHR Account Holder to capture information in preparation for an encounter with a provider and to support ongoing interactions with that provider. The system should enable the PHR Account Holder to request appointments with health care providers and capture information in preparation for the encounter.
The PHR Account Holder may fulfill specific requests for data or obtain requested diagnostic studies prior to the formal encounter. This may include providing PHR-S access to the new provider. The provider could also communicate with various members of the PHR Account Holder's care team.
Example(s): The PHR Account Holder MAY fill out a current Review Of Systems (ROS) template questionnaire and specific chief complaint related questions as part of the History of Present Illness (HPI) prior to the encounter.
| PH.6.3#01 | dependent SHALL |
The system SHALL provide the ability to capture and maintain communications between providers and the PHR Account Holder and/or the PHR Account Holder's Proxy according to organizational policy and/or jurisdictional law. |
| PH.6.3#02 | SHOULD |
The system SHOULD provide the ability to manage scanned documents based on the document type (e.g., based on the quality, format, origin, completion status, or intended diagnostic use (e.g., a screening versus a diagnostic breast examination)). |
| PH.6.3#03 | SHOULD |
The system SHOULD provide the ability to capture and maintain communications (e.g., date, entity, or details of communication) that were originated by the PHR Account Holder or Authorized PHR User. |
| PH.6.3#04 | SHALL |
The system SHALL provide the ability to capture, maintain and render PHR authorization information (e.g., to support a designee's claim that the designee is authorized to receive PHR Account Holder-related health information). |
| PH.6.3#05 | SHOULD |
The system SHOULD render to the PHR Account Holder a notification of the arrival of a provider-originated communication. |
| PH.6.3#06 | SHOULD |
The system SHOULD provide the ability to exchange communications between providers and PHR Account Holders using a secure connection. |
| PH.6.3#07 | SHALL |
The system SHALL conform to PH.6.3 (Communication Between Provider and PHR Account Holder and/or the PHR Account Holder's Representative) in order to exchange information. |
| PH.6.3#08 | SHALL |
The system SHALL conform to TI.1.8 (Patient Privacy and Confidentiality) to support adherence to various levels of confidentiality when exchanging information. |
| PH.6.3#09 | SHOULD |
The system SHOULD provide the ability to tag a set of elements within the PHR Account Holder's self-generated care plan that the PHR Account Holder intends to send to selected care team members. |
| PH.6.3#10 | conditional SHOULD |
IF the PHR Account Holder is creating a self-generated care plan, THEN the system SHOULD provide the ability for the PHR Account Holder to tag a set of selected care team members (to whom the PHR Account Holder intends to send certain information). |
| PH.6.3#11 | SHOULD |
The system SHOULD provide the ability to transmit a tagged set of elements within the PHR Account Holder's self-generated care plan to a tagged set of selected care team members. |
FHIR{
"resourceType" : "Requirements",
"id" : "PHRSFMR2-PH.6.3",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>The system should enable the PHR Account Holder to capture information in preparation for an encounter with a provider and to support ongoing interactions with that provider. The system should enable the PHR Account Holder to request appointments with health care providers and capture information in preparation for the encounter.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>The PHR Account Holder may fulfill specific requests for data or obtain requested diagnostic studies prior to the formal encounter. This may include providing PHR-S access to the new provider. The provider could also communicate with various members of the PHR Account Holder's care team.</p>\n<p>Example(s): The PHR Account Holder MAY fill out a current Review Of Systems (ROS) template questionnaire and specific chief complaint related questions as part of the History of Present Illness (HPI) prior to the encounter.</p>\n</div></span>\n \n\n \n <span id=\"actors\"><b>Actors:</b><br/> ehr</span>\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.6.3#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to capture and maintain communications between providers and the PHR Account Holder and/or the PHR Account Holder's Proxy according to organizational policy and/or jurisdictional law.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.6.3#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to manage scanned documents based on the document type (e.g., based on the quality, format, origin, completion status, or intended diagnostic use (e.g., a screening versus a diagnostic breast examination)).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.6.3#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture and maintain communications (e.g., date, entity, or details of communication) that were originated by the PHR Account Holder or Authorized PHR User.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.6.3#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to capture, maintain and render PHR authorization information (e.g., to support a designee's claim that the designee is authorized to receive PHR Account Holder-related health information).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.6.3#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD render to the PHR Account Holder a notification of the arrival of a provider-originated communication.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.6.3#06</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to exchange communications between providers and PHR Account Holders using a secure connection.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.6.3#07</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL conform to PH.6.3 (Communication Between Provider and PHR Account Holder and/or the PHR Account Holder's Representative) in order to exchange information.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.6.3#08</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL conform to TI.1.8 (Patient Privacy and Confidentiality) to support adherence to various levels of confidentiality when exchanging information.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.6.3#09</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to tag a set of elements within the PHR Account Holder's self-generated care plan that the PHR Account Holder intends to send to selected care team members.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.6.3#10</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n <i>conditional</i>\n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>IF the PHR Account Holder is creating a self-generated care plan, THEN the system SHOULD provide the ability for the PHR Account Holder to tag a set of selected care team members (to whom the PHR Account Holder intends to send certain information).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.6.3#11</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to transmit a tagged set of elements within the PHR Account Holder's self-generated care plan to a tagged set of selected care team members.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode" : "ehr"
}
],
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-PH.6.3",
"version" : "2.0.1-ballot",
"name" : "PH_6_3_Communications_Between_Provider_and_PHR_Account_Holder_and_or_PHR_Account_Holder_Proxy",
"title" : "PH.6.3 Communications Between Provider and PHR Account Holder and/or PHR Account Holder Proxy (Function)",
"status" : "active",
"date" : "2025-04-03T15:15:30+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "The system should enable the PHR Account Holder to capture information in preparation for an encounter with a provider and to support ongoing interactions with that provider. The system should enable the PHR Account Holder to request appointments with health care providers and capture information in preparation for the encounter.",
"purpose" : "The PHR Account Holder may fulfill specific requests for data or obtain requested diagnostic studies prior to the formal encounter. This may include providing PHR-S access to the new provider. The provider could also communicate with various members of the PHR Account Holder's care team.\r\n\r\nExample(s): The PHR Account Holder MAY fill out a current Review Of Systems (ROS) template questionnaire and specific chief complaint related questions as part of the History of Present Illness (HPI) prior to the encounter.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "PHRSFMR2-PH.6.3-01",
"label" : "PH.6.3#01",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to capture and maintain communications between providers and the PHR Account Holder and/or the PHR Account Holder's Proxy according to organizational policy and/or jurisdictional law."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.6.3-02",
"label" : "PH.6.3#02",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to manage scanned documents based on the document type (e.g., based on the quality, format, origin, completion status, or intended diagnostic use (e.g., a screening versus a diagnostic breast examination))."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.6.3-03",
"label" : "PH.6.3#03",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture and maintain communications (e.g., date, entity, or details of communication) that were originated by the PHR Account Holder or Authorized PHR User."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.6.3-04",
"label" : "PH.6.3#04",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to capture, maintain and render PHR authorization information (e.g., to support a designee's claim that the designee is authorized to receive PHR Account Holder-related health information)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.6.3-05",
"label" : "PH.6.3#05",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD render to the PHR Account Holder a notification of the arrival of a provider-originated communication."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.6.3-06",
"label" : "PH.6.3#06",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to exchange communications between providers and PHR Account Holders using a secure connection."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.6.3-07",
"label" : "PH.6.3#07",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL conform to PH.6.3 (Communication Between Provider and PHR Account Holder and/or the PHR Account Holder's Representative) in order to exchange information."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.6.3-08",
"label" : "PH.6.3#08",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL conform to TI.1.8 (Patient Privacy and Confidentiality) to support adherence to various levels of confidentiality when exchanging information."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.6.3-09",
"label" : "PH.6.3#09",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to tag a set of elements within the PHR Account Holder's self-generated care plan that the PHR Account Holder intends to send to selected care team members."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.6.3-10",
"label" : "PH.6.3#10",
"conformance" : [
"SHOULD"
],
"conditionality" : true,
"requirement" : "IF the PHR Account Holder is creating a self-generated care plan, THEN the system SHOULD provide the ability for the PHR Account Holder to tag a set of selected care team members (to whom the PHR Account Holder intends to send certain information)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.6.3-11",
"label" : "PH.6.3#11",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to transmit a tagged set of elements within the PHR Account Holder's self-generated care plan to a tagged set of selected care team members."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.